%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Propose an external tool}
\label{sec:propose_tool}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent Because \textsf{MS Visio} maps have some description limitation, one
part of our project was to identify different tools which exist on the
market and make a recommandation to \MARS{}.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Why using a tool ?}
\label{sec:why_using_a_tool}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent \textsf{MS Visio} has some limitation:
\begin{itemize}
\item Unique representation, it's not possible to draw different views
for different needs (or take a lot of time);
\item Difficulties to type flows on the graph;
\item No synchronisation between maps and inventory documents (problem
of double typing);
\item Difficulties to link application and infrastructure;
\item Difficulties to do impact analysis;
\item Difficulties to broadcast the maps and communicate it.
\end{itemize}

By using a dedicated tool,\MARS{} can have all the above missing
points of \textsf{MS Visio}. With this tool \MARS{} should be able to
describe and classify all fonctionnal and architecture elements of his
information system.

By using a tool, the business will take advantage like:
\begin{itemize}
\item Improve the knowledge sharing;
\item Help to decide on strategic decision;
\item Have a better referential to store all information about
application and infrastructure;
\item Communicate the results (maps or extracts of the
referential) to the business area.
\end{itemize} 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Stakeholder needs}
\label{sec:tool_stakeholder_needs}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent You can learn more about stakeholder needs in
section~\ref{sec:stakeholder_list}. We asked them about their needs
and build a small property list you can see in
table~\ref{tab:tool_properties}.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Different tools}
\label{sec:different_tools}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent In this section, we will talk about the different tool existing on the
market. We were focusing on the solutions that might answer the
stakeholders' needs.

\subsubsection{Market status}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent More and more sofware editors are trying to insert on the modeling
tools market. You can see in figure~\ref{fig:tools_quadrant} from
\textsf{Gartner}, the market status in January 2006.

\begin{figure}[!htbp]
	\centering
	\includegraphics[width=9cm]{graph/tools_quadrant_2006}
	\caption{Quadrant for business process analysis tool}
	\label{fig:tools_quadrant}
\end{figure}


\subsubsection{Short list}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent We built a short list based on our own work, we were looking at the
solution from the web, from discussion with ITIL teacher. We called
the supplier, and ask them a lot of question regarding their
solution. Most of time no evaluation version were available, but we
had enougth answer by phone to make a first evaluation without a lot
of technical details.


\subsubsection{Comparison between the different solutions}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent Table~\ref{tab:tool_properties} present the different properties for
each tool we decided to analyse.

\begin{description}
\item[Multi-user] means that several user can use the application
simultaneously, doing different things at the same time. These
different users can have different profiles, with different rights.
\item[DB] means that the application is based on a database.
\item[Versionning] means that the application can store the situation
at several times. With this, we are able to see the differences
between a past situation, the actual one and we are able to build
future views.
\item[Scheduler] means that high ressources operations such as graph
generation can be scheduled (e.g. during the night)
\item[Input] are the different ways the user can insert information
into the tool
\item[Import] are the different ways (file format) the user can import
data into the tool.
\item[Output (request)] are the differents ways (file format) the user
can extract data from the tool.
\item[Output] are the differents ways the application does its
reports.
\item[Publication] are the differents ways the application can
publicate the information to the different users.
\item[Price] is only the cost of the application without support or
upgrades
\item[Automatic diagram generation] is the availibity to produce
automatically the \SM{} diagrams from the repository.database.
\item[Requierements] that are mandatory to run properly the tool.
\end{description}

\begin{landscape}
\begin{table}
\begin{tabular}{|>{\raggedright}m{3.2cm}|l|l|l|>{\raggedright}m{4cm}|}
\hline
\tbf{Property/Tool}&\tbf{Solu QIQ}&\tbf{Envision IT}&\tbf{Aris IT Architect}&\tbf{AMARCO}\tbl\hline
Company         & AB+ Conseil        & Case France     & IDS Sheer          & Sysoft         \tbl\hline
Multi-user      & yes                & yes             & yes                & yes            \tbl\hline
DB              & Access/SQL server  & RDM RAIMA       & yes                   & yes            \tbl\hline
Versionning     & yes                & yes             & no                    & yes            \tbl\hline
Scheduler       & yes                & yes             & no                   & no             \tbl\hline
Input           & forms + graph      & forms + graph   & forms           & forms + graph  \tbl\hline
Import          & .xls .mdb .xml     & .xls .xml ASCII & .xls                   & no             \tbl\hline
Output(request) & .xls .mdb .xml     & .xls .xml ASCII &  .xls .xml                 & .xls          \tbl\hline
Publication     & HTML/Word          & HTML/Word       & HTML                   & HTML (zoom/search)  \tbl\hline
Price           & 55k\eur{}          & 9k\eur{}        & ?                   & 1200\eur{}/year  \tbl\hline
Maintenance (1year) &                & 1k\eur{}        & ?                   & 300\eur{}/months  \tbl\hline
Automatic diagram generation & yes   &                 &                    & yes \tbl\hline
Requirements    & Access or SQL server &               &                    & XP, Visio\&Access 2003 or SQL server \tbl\hline
\end{tabular}
\caption{Comparison between tool properties}
\label{tab:tool_properties}
\end{table}
\end{landscape}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Our recommandation}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent We don't have a complete view of the market, and we only identified
few solutions, but in the short list we just presented, after asking
for commercial and technical aspects, we decide to recommend \tbf{Solu
  QIQ}. This solutions seems to be the best one regarding the
stakholders needs.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Specifications for a tool}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent You can refer the annexe~\ref{an:tool_specifications},
page~\pageref{an:tool_specifications} for more details on the
specification about the tool we are looking for in order to manage the
\SM{}.
